Add the per-binding generator policy doc#32
Merged
Ar-mie merged 1 commit intoJul 9, 2026
Conversation
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
9fd4aaa to
6fb82bc
Compare
Ar-mie
approved these changes
Jul 9, 2026
Ar-mie
left a comment
Ar-mie
left a comment
Collaborator
There was a problem hiding this comment.
Approved but maybe regen-from-pin.sh probably should fail (exit 1) instead of just raising a warning, and the doc in compose-order.txt should be updated to fit the new order of merges that happened (#31 -> #33 -> #32)
also $PIN is never used in the script, only JMEOS_JAR uses it, is it a mistake (and a verification is missing) or made on purpose ?
estebanzimanyi
force-pushed
the
tooling/canonical-generator-policy
branch
from
6fb82bc to
41c7219
Compare
estebanzimanyi
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Documents how MobilityFlink is generated, under the ecosystem-wide per-binding
generator policy: every binding is a projection of the MEOS-API catalog and owns
its own in-repo generator.
GENERATION.mdstates the policy for this repo: MobilityFlink is a consumerbinding (it binds the JMEOS jar, not MEOS-API directly); its generator
tools/codegen_facades.pyemits theorg.mobilitydb.meos.MeosOps*forwarderfacades — a consumer projection that lives here so the JMEOS FFI line and the
facade line do not diverge.
Docs only — no code, no build impact.